Skip to content

engineering: fix cache extraction failure in win32 node_modules cache#293358

Closed
Copilot wants to merge 2 commits intojoao/turquoise-tahrfrom
copilot/sub-pr-293356
Closed

engineering: fix cache extraction failure in win32 node_modules cache#293358
Copilot wants to merge 2 commits intojoao/turquoise-tahrfrom
copilot/sub-pr-293356

Conversation

Copy link
Contributor

Copilot AI commented Feb 6, 2026

Second attempt after #291624 and revert #291740

When the cache key changes (e.g., cache salt update), the cache restore step creates .build/node_modules_cache/ but without cache.tzst inside. The extraction step then fails trying to extract a non-existent file:

tar (child): .build/node_modules_cache/cache.tzst: Cannot open: No such file or directory

Changes:

  • Added Test-Path check before tar extraction in Azure Pipelines win32 compile step
  • Added Test-Path check before tar extraction in GitHub Actions pr-win32-test workflow

This makes cache extraction resilient to cache key changes without requiring manual cache invalidation.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

The tar extraction was failing when the cache directory existed but the cache.tzst file didn't (e.g., after cache key change). Added a Test-Path check to only attempt extraction if the file exists.

Co-authored-by: joaomoreno <22350+joaomoreno@users.noreply.github.com>
Copilot AI changed the title [WIP] Update Windows node_modules caching to tar+zstd engineering: fix cache extraction failure in win32 node_modules cache Feb 6, 2026
Copilot AI requested a review from joaomoreno February 6, 2026 10:10
@joaomoreno joaomoreno closed this Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants